p broadband ai-2025-08-12
thumbnail (i.e. miniature image)
https://gyazo.com/e0f48877fe8880debe93a37f2806d74c
from Improvement of scatter plots for broadband AI.
p broadband ai-2025-08-12
What is a "Strong Opinion Group"?
https://gyazo.com/6d2f8649df7e08f061d790b197505efa
Demonstration of "This is what a strong opinion group is all about."
https://gyazo.com/a0b85b9d37d489cffb382e297fe5d3a9
In the case of large data sets, there are 400 or so dense opinion displays, so it's essentially absurd to label them all.
Fixed aspect ratio issues
https://gyazo.com/86105b223d96db8f243fbc0bdf204ea9
https://gyazo.com/27955affe4f412b410809ba27bd327e1
https://gyazo.com/13e48a4d126e7907446a5010c65b0a6b
https://gyazo.com/e0f48877fe8880debe93a37f2806d74c
Much better.
https://gyazo.com/2995bccf30e21af26bb2647fa9da1eff
Well, this seems inherently impossible.
You can see this experimental version here.
https://policy-pr-hub.vercel.app/kouchou-ai
dd2030 slack
nishio.icon
We have been thinking about how to take advantage of this new view, and now
Reporting Screen: Admin
All Reports List Screen: Admin
LISTED REPORTS LISTING SCREEN: Anyone
Report Screen: Anyone
but I'm wondering if we need an "administrator's report screen"? I'm starting to get the feeling that we need an "admin report screen".
Switch between various views on the administrator's report screen, change default settings, etc., and then "publish with these settings".
It is not correct that a mouse hover on a cluster brings up a detailed description of each point of the components, but it is correct that a mouse hover on a cluster brings up the details of the cluster and a click on the cluster brings up a narrowed-down view of that cluster.
(but you will need to use the back button)
Because it is limited to two layers, it is necessary to divide the data into 20 labels in one layer when there are 10,000 data or so. Essentially, the upper limit of labels that can be drawn is determined by human cognitive ability, and it would be correct to increase the number of layers when there is a lot of data so as not to exceed that limit.
If you think about the usefulness of the smartphone view, the current system of presenting information in hover is fundamentally wrong to begin with.
Putting in the HOVER listener seems to be the cause of the performance degradation in the PC version as well.
Should it basically be in menu form when clicked or tapped?
Maybe the area map should be the first thing shown in the phone view?
Maybe even on PC (in the sense of reducing the initial waiting time).
---
This page is auto-translated from /nishio/p広聴AI-2025-08-12 using DeepL. If you looks something interesting but the auto-translated English is not good enough to understand it, feel free to let me know at @nishio_en. I'm very happy to spread my thought to non-Japanese readers.